EDM Server Service Account Requirements For Oracle

Meridian uses a specific Oracle account to create the first vault in an Oracle instance. The account name must be MERIDIAN (upper case) and the initial password must be MANAGER (upper case).

The minimal privileges for this account are:

• Create Procedure
• Create Sequence
• Create Session
• Create Table
• Unlimited Tablespace

The Oracle roles that include these privileges are DBA and CONNECT. Although Unlimited Tablespace can be replaced with a quota, this can potentially be dangerous. If Meridian runs out of table space, the vault will be corrupted and must be restored from backup, potentially losing valuable data. The MERIDIAN account should always be able to store data in the Oracle database. To make sure that there is always enough space for MERIDIAN to store data in Oracle, do not use space limits on the data files or use large values for the Initial and Next size. It should be the responsibility of an Oracle database administrator to ensure that the MERIDIAN user in Oracle always has enough space to store data.

The EDM Server service will always use the account MERIDIAN to create the tables needed to store the vault metadata. The user MERIDIAN is therefore also the owner of these tables and should not be removed from the database.

When Oracle and Meridian are located on separate computers, the computer running the EDM Server service must be able to access the remote Oracle instance. You can do this either with the Net Configuration Assistant or editing the tnsnames.ora file directly. Refer to the Oracle documentation for more information.

After an Oracle instance has been created, a Meridian vault can be created in it. This is done in the usual way as described in Create a New Vault. After the creation of the first Oracle vault, you can change the password for the user MERIDIAN in Meridian Enterprise Administrator. This will change the password in Oracle as well.